While in here should we also address these problems?

test("Fails reasonably when no parameters passed to dynamic segment", function() {
  var router = new RouteRecognizer();
  router.add([{"path":"/posts","handler":"posts"},{"path":"/:secret/edit","handler":"edit"}], { as: "edit"})

  // Expects a second argument.
  router.generate("edit"); // => error, undefined is not an object

  // Expects a parameter of a particular name.
  router.generate("edit", {}); // => /posts/undefined
});

@nathanhammond - This seems reasonable to me, but we may want to include more information in the error message (handler.toString() or something?). Also, what happens in Ember today if you use an empty string for a glob/dynamic segment?

@rwjblue: What happens today: it happily generates a route when you pass an empty string and you can link-to to it, but blows up on refresh or open in new tab.

The latter one in my first comment can simply provide a better message for these scenarios.

This is complete. Assuming no further comments I intend to land it sometime this weekend. Review now! /cc @wycats @krisselden @mixonic

(Note: the messages are as good as they reasonably need to be, the stack trace will make it plenty clear what blew up.)

(Note: landing doesn't mean an immediate release, I intend to make sure that this goes the full span of an Ember canary to get as much feedback as possible on how often people end up broken.)

Given no additional feedback for two weeks, I'm landing this.